Skip to content

Conversation

@ncooke3
Copy link
Member

@ncooke3 ncooke3 commented Nov 25, 2025

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @ncooke3, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces initial UI testing capabilities for the StorageExample iOS application. It establishes a new UI test target within the Xcode project and provides two foundational UI test files: one for general UI interactions and another specifically for verifying the application's launch behavior. This work lays the groundwork for expanding UI test coverage and ensuring the stability of the application's user interface.

Highlights

  • New UI Test Target: A new UI test target named "StorageExample (iOS) UITests" has been added to the Xcode project, enabling UI testing for the iOS application.
  • Basic UI Test File Added: A boilerplate StorageExample__iOS__UITests.swift file was introduced, containing standard setup and teardown methods, along with a basic testExample that launches the application.
  • Launch UI Test File Added: A dedicated StorageExample__iOS__UITestsLaunchTests.swift file was added to specifically test the application's launch process, including capturing a screenshot upon launch for visual verification.
  • Xcode Project Configuration: The project.pbxproj file was extensively updated to integrate the new UI test target, including adding file references, build phases, target dependencies, and build configurations for both Debug and Release schemes.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a new UI test target and corresponding template files for the iOS StorageExample. My review focuses on improving the boilerplate code in the newly added test files. I've suggested removing unnecessary comments, adding required calls to super in setUpWithError methods, and making the placeholder test more meaningful. These changes will improve the correctness and readability of the new test code.

Comment on lines +19 to +26
override func setUpWithError() throws {
// Put setup code here. This method is called before the invocation of each test method in the class.

// In UI tests it is usually best to stop immediately when a failure occurs.
continueAfterFailure = false

// In UI tests it’s important to set the initial state - such as interface orientation - required for your tests before they run. The setUp method is a good place to do this.
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

Boilerplate comments should be removed to improve readability. Also, it's required to call super.setUpWithError() when overriding this method.

    override func setUpWithError() throws {
        try super.setUpWithError()
        continueAfterFailure = false
    }

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ncooke3 I think you can just delete all the generated override stubs in this file.

Comment on lines +28 to +30
override func tearDownWithError() throws {
// Put teardown code here. This method is called after the invocation of each test method in the class.
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

This method is empty, but when overriding tearDownWithError, you must call super.tearDownWithError(). Since there is no other teardown logic, this method can be removed entirely. If you intend to add logic later, ensure you include the super call.

@ncooke3 ncooke3 requested a review from morganchen12 December 16, 2025 20:01
@ncooke3
Copy link
Member Author

ncooke3 commented Dec 16, 2025

Not sure why the check is failing. I'll consider it non-blocking.

nickcooke@nickcooke-mac2 quickstart-ios (nc/strg-tests) % ../firebase-ios-sdk/scripts/style.sh storage/StorageExample_iOS_UITests/StorageExampleUITests.swift storage/StorageExample_iOS_UITests/StorageExampleUITestsLaunchTests.swift
nickcooke@nickcooke-mac2 quickstart-ios (nc/strg-tests) % git status
On branch nc/strg-tests
Untracked files:
  (use "git add <file>..." to include in what will be committed)
	build-for-testing/
	rename_prompt.md
	suffixed_targets.txt

nothing added to commit but untracked files present (use "git add" to track)
nickcooke@nickcooke-mac2 quickstart-ios (nc/strg-tests) % 

Comment on lines +19 to +26
override func setUpWithError() throws {
// Put setup code here. This method is called before the invocation of each test method in the class.

// In UI tests it is usually best to stop immediately when a failure occurs.
continueAfterFailure = false

// In UI tests it’s important to set the initial state - such as interface orientation - required for your tests before they run. The setUp method is a good place to do this.
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ncooke3 I think you can just delete all the generated override stubs in this file.

@ncooke3 ncooke3 merged commit b07c22a into main Dec 16, 2025
7 of 8 checks passed
@ncooke3 ncooke3 deleted the nc/strg-tests branch December 16, 2025 20:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants